Technote Number: 1093237
Problem:
This issue was reported to Lotus Software Quality Engineering and has been
addressed in Domino for iSeries MU R5.07a.
As a temporary workaround, remove OS/400 PTF SF65118. Note, however, that this
will cause errors to be logged in the joblog of the job that runs the agents
and will cause the return of trailing spaces with DB2 data. For further
information on this, refer to the document titled "Domino for AS/400: LEI Does
Not Trim Spaces as Expected" (#:1099321).
Another temporary workaround is to make sure any LSXODBC-based agent is
launched before an LSXLC-based agent and/or disable the DECS Activity that is
monitoring the Notes database.
Supporting Information:
The failure can be identified through the use of the GetExtendedErrorMessage
method, which will report the following message:
Addin: Agent printing: UpdateRow Error#: 720
Addin: Agent printing: Res.GetErrorMessage:LS:DO- ODBC could not complete the
requested operation.
Addin: Agent printing: Res.GetExtendedErrorMessage:Column <column name> not in
specified tables
The <column name> listed will be truncated. For example, Column name CUSNUM
will be truncated to CUSNU.
Or, if not using GetExtendedErrorMessage, then the error can also be determined
with the use of the LSXODBC_GDF_LEVEL setting.
Set Config LSXODBC_GDF_LEVEL=2 will enable detailed ODBC information in the
server console and LOG.NSF. With this setting, the following error will be
generated:
"QTDebugGetError: after SQLERROR, retcode from SQLERROR is = 0
: -206 <Column CUSNU not in specified tables>"
The SQLERROR return code indicates an SQL0206 error.
Related Documents:
Domino for AS/400: LEI Does Not Trim Spaces as Expected
Document #: 1099321 More >
|  |
|
|
|
|
|